<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type='text/xsl' href='../../../../assets/comments.xslt'?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:thr="http://purl.org/syndication/thread/1.0" xml:lang="de-DE">
  <title>💬 <![CDATA['WordPress => Hugo']]></title>
  <subtitle type="text">Marcus Rohrmoser mobile Software</subtitle>
  <updated>2019-05-19T19:14:42Z</updated>
  <link rel="self" type="application/atom+xml" href="https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml"/>
  <id>https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml</id>
  <entry>
    <title>💬 <![CDATA['WordPress => Hugo']]></title>
    <author>
      <name><![CDATA[Poorchop]]></name>
    </author>
    <id>https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml#comment-001</id>
    <updated>2021-04-11T08:59:03Z</updated>
    <content type="text"><![CDATA[It seems that over the past decade, a lot of people have been switching to static site generators but having previously used one myself, I've been tempted to move over to WordPress or another CMS. I'm amazed at how much they're capable of doing and I still think that comment forms are extremely valuable. The best part of these content management systems is that commenting usually works fine without Javascript so visitors with Javascript disabled still get the full experience. Plus there's no dependence on a third party like Disqus.

I find that people are very much not inclined to submit comments and feedback via e-mail. I normally wouldn't do something like this either but I have been making an exception recently for a few reasons. If ShaarliGo utilizes CGI then I'm surprised that you haven't implemented comments via CGI. I have started working on a FastCGI script in order to add comments to my site but I hardly have time to work on it and it will pale in comparison to existing solutions like WordPress comments. I think that dynamic backends are underrated. There is tremendous potential in server-side scripting and being able to deliver dynamic content without using any Javascript whatsoever is pretty great.
]]></content>
    <thr:in-reply-to ref="https://blog.mro.name/2019/05/wp-to-hugo-making-of/" href="https://blog.mro.name/2019/05/wp-to-hugo-making-of/" type="text/html"/>
  </entry>
  <entry>
    <title>💬 <![CDATA['WordPress => Hugo']]></title>
    <author>
      <name><![CDATA[mro]]></name>
    </author>
    <id>https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml#comment-002</id>
    <updated>2021-04-11T09:14:03Z</updated>
    <content type="text"><![CDATA[Thanks for your comment,
yes, I agree that email feels awkward as a feedback channel for blogposts. IMO the biggest disadvantage is the availability of an email client when reading the blogpost. And that the blog-host learns the email address and has to handle it carefully. But the latter is also common practice elsewhere.

But for me as a blog-host it was the most trivial thing to start with and so I tried that. The workflow on my side is also not streamlined yet and a bit cumbersome. Has to be tuned once volume increases. 

Recently I made a trivial form-post-processing based on server-side form dumps and processing alongside the static site generator: https://codeberg.org/mro/form2xml.

That could run scheduled and unattended and publish the comments if desired. Something similar happens here with items in a shop https://codeberg.org/mro/flohmarkt.monte-ts.de/src/branch/master/app/cron.sh

Nice you mention shaarli – a post on your own shaarli about a post or comment here indeed should do a webmention, activitypub or the like and appear here in context, too.

That's what I aim for with https://demo.mro.name/shaarligo. Static microblogs talking to each other meshing into the fediverse.

And still without mandatory Javascript on the client-side as seen here. Optional for improved UX is fine, though. 
]]></content>
    <thr:in-reply-to ref="https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml#comment-001" href="https://blog.mro.name/2019/05/wp-to-hugo-making-of/comments.xml#comment-001" type="text/html"/>
  </entry>
  <entry>
    <title>💬 <![CDATA[]]></title>
    <author>
      <name><![CDATA[mro]]></name>
    </author>
    <id>https://blog.mro.namecomments.xml#c2</id>
    <updated>2024-03-15T23:43:51+01:00</updated>
    <content type="text"><![CDATA[Today finally all comments are valid https://mro.name/code/blog.mro.name/commit/bc140f271]]></content>
    <thr:in-reply-to ref="https://blog.mro.name" href="https://blog.mro.name" type="text/html"/>
  </entry>
</feed>
